Credential Acquisition

Your end users must upload the required credentials and trigger the workflow that evaluates the credentials. Jumio refers to this process as the "customer journey" and provides several integration channels you can use to implement it. These include:

  • A Web Client you can embed in your web application. The Jumio Web Client provides clear guidance to your end-users and manages the interactions with the end-users camera and other device features.

  • Jumio SDKs. The SDKs provide a complete default implementation of the customer journey, and also support customizations.

  • REST APIs for Credential Acquisition for uploading credentials and finalizing the workflow. Your application can call the APIs directly when you need to control the other aspects of the customer journey

Depending on the workflow you also upload supporting dataClosed Data uploaded in addition to an ID or Document that helps to identify the end user. These are typically values such as a phone number or email address that cannot be extracted from the ID. in addition to an ID, Document, Selfie, and/or Facemap. Supporting data is used for enhanced fraud detection and to provide additional validation checks for extracted data. See Uploading Supporting Data.

Regardless of which implementation channel(s) you choose to use, all transactions are initiated by a REST API call to create or update an account. See Creating or Updating Accounts. The response from the call includes the tokens and URLs described in the following topics.
Jumio software is currently not designed to work with kiosk solutions. Features such as taking a picture of the ID document and selfie will not function properly and may impact the user experience, quality and accuracy. This includes iPads or other tablets that are operating in a mounted setup.